Pull Request Description

Finally this pull request proposes --inspect option to allow debugging of .enso in Chrome Developer Tools:

enso$ ./built-distribution/enso-engine-0.0.0-dev-linux-amd64/enso-0.0.0-dev/bin/enso --inspect --run ./test/Tests/src/Data/Numbers_Spec.enso 
Debugger listening on ws://127.0.0.1:9229/Wugyrg9Nm4OUL9YhzdcElmLft71ayZW3LMUPCdPyNAY
For help, see: https://www.graalvm.org/tools/chrome-debugger
E.g. in Chrome open: devtools://devtools/bundled/js_app.html?ws=127.0.0.1:9229/Wugyrg9Nm4OUL9YhzdcElmLft71ayZW3LMUPCdPyNAY

copy the printed URL into chrome browser and you should see:

One can also debug the .enso files in NetBeans or VS Code with Apache Language Server extension just pass in special JVM arguments:

enso$ JAVA_OPTS=-agentlib:jdwp=transport=dt_socket,server=y,address=8000 ./built-distribution/enso-engine-0.0.0-dev-linux-amd64/enso-0.0.0-dev/bin/enso --run ./test/Tests/src/Data/Numbers_Spec.enso
Listening for transport dt_socket at address: 8000

and then Debug/Attach Debugger. Once connected choose the Toggle Pause in GraalVM Script button in the toolbar (the "G" button):

and your execution shall stop on the next .enso line of code. This mode allows to debug both - the Enso code as well as Java code.

Originally started as an attempt to write test in Java:

• test written in Java
• support for JUnit in build.sbt
• compile Java with -g - so it can be debugged
• Implementation of StatementNode - only gets created when materialize request gets to BlockNode

Important Notes

Checklist

Please include the following checklist in your PR:

• [ x ] The documentation has been updated if necessary.
• [ x ] All code conforms to the Scala, Java, and Rust style guides.
• All code has been tested:
  • [ x ] Unit tests have been written where possible.